Add myvibe skill#1779
Open
Mohamed201389 wants to merge 2 commits into
Open
Conversation
Adds a vendor-neutral one-shot intake plus deterministic plan/scaffold/build/test/ship loop for new project creation from a single one-line command.
github-actions
Bot
added
new-submission
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
main, but PRs should target staged.
The main branch is auto-published from staged and should not receive direct PRs.
Please close this PR and re-open it against the staged branch.
You can change the base branch using the Edit button at the top of this PR,
or run: gh pr edit 1779 --base staged
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new community skill, myvibe, intended to guide an agent through a deterministic one-shot intake and a plan→scaffold→build→test→ship loop for greenfield project creation, and updates the generated skills index to include it.
Changes:
- Added
skills/myvibe/SKILL.mddefining the myvibe skill and its protocol. - Updated
docs/README.skills.mdto include the myvibe entry in the skills table.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| skills/myvibe/SKILL.md | Introduces the myvibe skill definition and step-by-step workflow. |
| docs/README.skills.md | Adds the generated index entry for the new myvibe skill. |
Comment on lines
+35
to
+60
| The kit lives at `https://github.com/Mohamed201389/myVibe`. After install, the kit folder is on disk and the agent follows files in this order. | ||
|
|
||
| ### Step 1 — Intake (ONE round) | ||
|
|
||
| 1. Read `INTAKE.md` in the kit folder. | ||
| 2. Fill the 18-section intake form with sensible defaults derived from the user's one-line command. | ||
| 3. Send the filled form to the user in a single message; ask them to override any line or reply "go". | ||
| 4. After "go", write the final form to `INTAKE.md` at the new project root and commit it as `chore: lock project intake`. | ||
| 5. Do not ask further questions until the project is shipped. If something is ambiguous mid-build, pick a sensible default and note it in `CHANGELOG.md`. | ||
|
|
||
| ### Step 2 — Orchestrate | ||
|
|
||
| Read `00-START-HERE.md` and follow Phases 2 through 7 in order. At each phase boundary, re-read the relevant per-stage file: | ||
|
|
||
| - `01-plan.md` for planning | ||
| - `03-scaffolding.md` for stack and bootstrap | ||
| - `05-frontend.md` / `06-backend.md` / `07-database.md` for the foundation | ||
| - `04-features.md` for each feature spec | ||
| - `08-testing.md` for test strategy | ||
| - `09-checkpoint.md` at every checkpoint | ||
| - `10-changelog.md` for changelog discipline | ||
| - `11-localhost.md` for env, ports, dev DX | ||
| - `12-code-style.md` for code quality | ||
| - `13-debugging.md` when something breaks | ||
| - `14-quality-gates.md` before declaring done | ||
|
|
| | [mvvm-toolkit](../skills/mvvm-toolkit/SKILL.md)<br />`gh skills install github/awesome-copilot mvvm-toolkit` | CommunityToolkit.Mvvm (the MVVM Toolkit) core: source generators ([ObservableProperty], [RelayCommand], [NotifyPropertyChangedFor], [NotifyCanExecuteChangedFor], [NotifyDataErrorInfo]), base classes (ObservableObject / ObservableValidator / ObservableRecipient), commands (RelayCommand / AsyncRelayCommand), and validation. Companion skills: mvvm-toolkit-messenger for pub/sub, mvvm-toolkit-di for Microsoft.Extensions.DependencyInjection wiring. Works across WPF, WinUI 3, MAUI, Uno, and Avalonia. | `references/end-to-end-walkthrough.md`<br />`references/relaycommand-cookbook.md`<br />`references/source-generators.md`<br />`references/troubleshooting.md`<br />`references/validation.md` | | ||
| | [mvvm-toolkit-di](../skills/mvvm-toolkit-di/SKILL.md)<br />`gh skills install github/awesome-copilot mvvm-toolkit-di` | Wire CommunityToolkit.Mvvm ViewModels into Microsoft.Extensions.DependencyInjection. Covers the .NET Generic Host composition root, constructor injection, service lifetimes (Singleton / Transient / Scoped), IMessenger registration, resolving ViewModels in Views, keyed services, testing seams, and the legacy Ioc.Default escape hatch. Use across WPF, WinUI 3, .NET MAUI, Uno, and Avalonia. | `references/dependency-injection.md` | | ||
| | [mvvm-toolkit-messenger](../skills/mvvm-toolkit-messenger/SKILL.md)<br />`gh skills install github/awesome-copilot mvvm-toolkit-messenger` | CommunityToolkit.Mvvm Messenger pub/sub for decoupled communication between ViewModels (or any objects). Covers WeakReferenceMessenger vs StrongReferenceMessenger, IRecipient<TMessage>, RequestMessage<T> / AsyncRequestMessage<T> / CollectionRequestMessage<T>, ValueChangedMessage<T>, channels (tokens), and the ObservableRecipient activation lifecycle. Use across WPF, WinUI 3, .NET MAUI, Uno, and Avalonia. | `references/messenger-patterns.md` | | ||
| | [myvibe](../skills/myvibe/SKILL.md)<br />`gh skills install github/awesome-copilot myvibe` | Use this skill when the user gives a one-line command to start a new project, such as "build me a kanban board", "scaffold a SaaS dashboard", "make a portfolio site", "create an inventory tracker", "vibe code", or "use myVibe". Runs a one-shot intake that collects every project decision in a single round, then plans, scaffolds, builds, tests, and ships a complete localhost-running project. Do not trigger for edits to existing projects, single-file requests, bug fixes, or pure questions — this skill is for new project creation only. | None | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new skill,
myvibe, under skills/myvibe/.What it does
myvibe is a vendor-neutral skill that turns a one-line project command (e.g. 'build me a kanban app') into a complete, tested, localhost-running project. It uses a one-shot intake (all decisions collected upfront in a single round), then runs plan -> scaffold -> build -> test -> ship with a Ralph-style feature loop and a binary quality gate.
Why it fits
This is not a 'tell Copilot how to write TypeScript' submission. It addresses a specific gap frontier models do not handle well by default: a deterministic intake/plan/build/test/ship loop for new project creation that prevents the common failure modes (random stack picks, mid-build interrogation, skipped tests, half-shipped features).
Validation
npm run skill:validatepasses (339 skills valid, including myvibe)npm run buildregenerated docs/README.skills.md to include the new entry